Upload M365 Users from File and Attach to Template

You can upload a list of M365 users from an external file and attach them to a specific template.

To import a bulk template from a CSV file:
1. From the template drop-down list, choose a template to import.

Graphical user interface, application

Description automatically generated

Graphical user interface, application

Description automatically generated

2. From the Add Policy drop-down, select the desired policy.
3. Enable Enterprise Voice.
4. From the Assign Number from drop-down, choose File.

5. Click Submit All Changes. The Import File button is enabled. This action is required whenever a change is made to a policy.
6. Click Import File to import a template file.

Graphical user interface, text, application, email

Description automatically generated

7. Click Import CSV. The Import file dialog is displayed.

Graphical user interface, application

Description automatically generated

The file to import should be in the following format:

Copy
sip:christiec@m365x74218585.onmicrosoft.com,+18585550111
sip:irvins@m365x74218585.onmicrosoft.com,+13095550101
sip:gradya@m365x74218585.onmicrosoft.com,+13095550104
sip:alexw@m365x74218585.onmicrosoft.com,+18585550110
8. Choose a file to import.

Graphical user interface, application

Description automatically generated

9. Optionally select the CSV column to apply to the SIP address and Number fields.
10. Select Import <number of records> records.

Graphical user interface, text, application

Description automatically generated

11. Select all records and then click Apply Template.

Graphical user interface, text, application

Description automatically generated

The following confirmation is displayed.

Graphical user interface, text, application, email

Description automatically generated

The operation is now completed. You can view the cmdlets in the Queued Changes menu (see Monitoring M365 Replication Actions Queue).

A validation check is conducted to verify whether a user already has a preexisting policy in the Managed Template. In this case, the cmdlet is not populated in the Queued Changes for this user, thereby avoiding the loading of redundant cmdlets to the replication queue.